Methods, systems, and media to expand resources available to a logical partition

ABSTRACT

Methods, systems, and media to expand resources available to logical partition associated with a client are contemplated. Embodiments may associate the logical partition with a grid that retains a list of resources, referred to as grid resources, available for allocation to logical partitions. The grid resources may include resources from, e.g., other logical partitions within the logically partitioned system, logical partitions from other logically partitioned systems, another type of system, a cluster, and the like. Further, one or more of the systems associated with the grid may include on-demand resources that are also available to supplement resources based upon the demands of the client. Embodiments may also monitor resource usage by the client and meter billable usage of the grid resources and/or on-demand resources based upon agreements between service providers and clients.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention generally relates to the field of computers. Moreparticularly, the present invention relates to methods, systems, andmedia for expanding resources available on computers.

2. Description of the Related Art

Parallel processing generally refers to performing multiple computingtasks in parallel. Traditionally, parallel processing required multiplecomputer systems with the resources of each computer system dedicated toa specific task or allocated to perform a portion of a common task.However, recent advances in computer hardware and software technologieshave resulted in single computer systems capable of performing highlycomplex parallel processing by logically partitioning the systemresources to different tasks. In a logically partitioned (“LPAR”)computer system, available system resources are allocated among multiplesets of resources so that each set of resources can be operatedindependently of the other. The task of splitting these resources amonglogical partitions is typically accomplished via a layer of softwarecomponents commonly referred to as a partition manager.

One objective of a partition manager is to allow each logical partitionto run software, such as operating systems and operating system specificapplications, that are typically developed to run on a dedicatedcomputer system with little or no modification. For example, a systemadministrator may want one logical partition to run IBM's OS/400operating system, a second logical partition to run IBM's AIX operatingsystem, and a third logical partition to run the LINUX operating system.By providing the ability to run multiple operating systems on the samecomputer system, a logically partitioned computer system may provide auser with a great deal of freedom to choose the application softwarebest suited to the users' need and with little or no regard to theoperating system for which the application program was written.

One market for logically partitioned systems is a person or company,hereinafter referred to as a host service provider, that providesinformation technology (“IT”) services to clients or customers, such asother individuals or groups within the same company or in othercompanies. The host service provider typically maintains the logicallypartitioned system and rents the logical partitions to the clients. Theclients can then use one or more of the logical partitions as a networkserver, web server, and/or the like. The host service provider may alsooffer additional services, such as installing or de-installing software,updating software, adding or replacing hardware, data backup, and otherIT services.

The host service provider typically charges the clients a negotiated feefor the equipment and services. When the clients are part of the sameorganization as the host service provider, the clients may have defaultagreements through rules set up by the organization and may be billedvia charge accounts, or the like, that are associated with variousgroups within the organization. An accounting group for the organizationmay then handle the charges attributed to the charge accounts byadjusting budgets. In other situations, where the client is anothercompany, the clients may execute contracts with the host serviceprovider that outline rates for different services and get billeddirectly.

Clients associated with a host service provider can expand the resourcesavailable to their partition requesting additional services byre-negotiating the agreement with the host service provider, eitherdirectly with the host service provider or through other channels withinan organization. For instance, as the client's business expands, theclient may need more processing capacity, memory, hard drive space,etc., to keep up with the demands placed on the client's logicalpartition. The client may gauge the amount of resources to add basedupon usage of current resources and decide that it is time to add theresource when the usage reaches a utilization threshold of the localpartition's current resources.

One problem many clients experience is that conventional systems do noteasily accommodate seasonal and/or periodic fluctuations in resourcedemands, or sharp increases in resource demands. For instance, clientsthat purchase or contract for resources to sufficient accommodateseasonal fluctuations find that these resources are significantlyunderutilized during the off-season. Similarly, clients that realizesharp increases in demand for resources are frequently compelled bypotential losses of business and/or profits to expand quickly, and arethus placed in a disadvantageous position for purchasing orre-negotiating an agreement for resources.

The negative effect of fluctuating demand is not limited to the clients.The host service provider that provides the logical partitions maximizesprofits (or maintains a budget) by trying to sell or lease the use ofall the available resources in a logically partitioned system. Thus, thehost service provider is unable to fully accommodate seasonal oremergency requests from its clients without maintaining its own sparecapacity and/or adding new equipment on an emergency basis. Theseproblems are compounded by the overhead associated with purchasing newequipment. For example, after purchasing a new logically partitionedsystem to accommodate the resource needs of a client, the host serviceprovider will often need to configure the new resources, and thentransfer software and data to the new system. This process can oftenrequire considerable time and expertise

Therefore, there is a need for methods, systems, and media to providemore flexibility to host service providers and clients to expandresources available to a logical partition without incurringsignificantly increased initial costs.

SUMMARY OF THE INVENTION

Embodiments of the invention generally provide methods, systems, andmedia for expanding resources available to a logical partition. Oneembodiment provides a method for expanding resources available to alogical partition associated with a client. The method generallyincludes associating partition resources of the logical partition with agrid; providing grid resources from the grid to the logical partitionbased upon usage of the partition resources, wherein the grid resourcesare available to the logical partition; and providing on-demandresources to the logical partition based upon the usage of the partitionresources and a usage of the grid resources when the grid resources areavailable to the logical partition.

Another embodiment provides a method for expanding resources availableto a logical partition associated with a client. The method may includeregistering resources with a grid as grid resources; allocating gridresources to the logical partition after utilization of partitionresources by the logical partition reaches a first utilizationthreshold; allocating on-demand resources to the logical partition afterthe logical partition reaches a second utilization threshold for thegrid resources; and billing the client for usage of the on-demandresources.

Another embodiment provides an apparatus for expanding resourcesavailable to a logical partition associated with a client of a systemhaving on-demand resources. The apparatus may include a grid associatorto associate the logical partition with a grid; a resource monitorcoupled with the grid associator to monitor usage of partition resourcesassociated with the logical partition and usage of grid resourcesassociated with the grid, and coupled with the on-demand resources toallocate the grid resources and the on-demand resources to the logicalpartition based upon utilization thresholds associated with thepartition resources and the grid resources; and a resource meter coupledwith the resource monitor to determine a first rate associated with anallocation of the on-demand resources to the logical partition forbilling the client.

A further embodiment provides a computer readable medium containing aprogram which, when executed, performs an operation. The operation mayinclude associating partition resources of a logical partition with agrid; providing grid resources from the grid to the logical partitionbased upon usage of the partition resources, wherein the grid resourcesare available to the logical partition; and providing on-demandresources to the logical partition based upon the usage of the partitionresources and usage of the grid resources when the grid resources areavailable to the logical partition.

Other embodiments provide a method for managing and controllingallocation of resources of a logical partition, and a method fordeploying a computer application on a host service provider system. Oneembodiment of a method for managing and controlling allocation ofresources of a logical partition comprises providing grid resources tothe logical partition based upon usage of the partition resources; andproviding on-demand resources to the logical partition based upon ausage of the partition resources and a usage of the grid resources. Theembodiment of a method for deploying a computer application on a hostservice provider system comprises installing an application on a logicalpartition of a computer system, the computer system having on-demandresources associated therewith; associating the logical partition with agrid, the grid having grid resources associated therewith; configuringthe computer system to provide the grid resources to the logicalpartition based upon usage of the partition resources; and configuringthe computer system to provide the on-demand resources to the logicalpartition based upon a usage of the partition resources and a usage ofthe grid resources.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above recited features, advantages andobjects of the present invention are attained and can be understood indetail, a more particular description of the invention, brieflysummarized above, may be had by reference to the embodiments thereofwhich are illustrated in the appended drawings.

It is to be noted, however, that the appended drawings illustrate onlytypical embodiments of this invention and are therefore not to beconsidered limiting of its scope, for the invention may admit to otherequally effective embodiments.

FIG. 1 is an embodiment of system including a logically partitionedsystem, other system(s), clients, and a manufacturer to expand theresources available to logical partitions.

FIG. 2 is an embodiment of a logically partitioned system having one ormore logical partitions, hardware resources, and on-demand resources toexpand the resources available to the one or more logical partitions.

FIG. 3 depicts an embodiment of a method for expanding the resourcesavailable to a logical partition.

FIG. 4 depicts an embodiment of a method for billing a client based uponusage of additional resources available to a logical partition.

FIG. 5 depicts an embodiment of a method for paying a client based uponusage of the client's resources, which are made available to a logicalpartition.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following is a detailed description of the embodiments of theinvention depicted in the accompanying drawings. These embodiments areexamples of how the invention may be implemented and are in such detailas to clearly communicate the invention. However, the amount of detailoffered is not intended to limit the anticipated variations ofembodiments, but on the contrary, the intention is to cover allmodifications, equivalents, and alternatives falling within the spiritand scope of the present invention as defined by the appended claims.The detailed descriptions below are designed to make such embodimentsobvious to a person of ordinary skill in the art.

Generally speaking, the present invention contemplates methods, systems,and media to expand and allocate resources available to a clientassociated with a logical partition, as well as methods for metering andcharging for these resources. Some embodiments of the present inventionassociate the logical partition with a grid that retains a list ofresources available for use by the logical partition. A grid, in turn,generally refers to an association between computer systems, storagedevices, logical partitions within the same logically partitionedsystem, logical partitions from another logically partitioned system,clusters of computer systems, I/O devices, and the like (referred tocollectively as “grid resources”) that are communicatively coupledtogether so that their capabilities can be shared/allocated among theparticipating systems. In this way, the clients associated with theparticipating partitions can enjoy the benefits of a very powerfulsystem without incurring the conventional costs of such a system.

In some embodiments, the client systems in the grid may act as a donorof grid services at various times. As compensation, these donor systemsmay be eligible to receive the benefits of being a participating systemand/or may receive contractual or monetary benefits, such as receiving acash payment for the use of their resources or a discount off the costfor using the grid's resources. Depending upon the particular gridarrangement, the systems that donate resources to the grid may or maynot retain control over how and when the resources are allocated. Forexample, a resource allocator for grid resources in some embodiments mayhave to request the use of grid resources from the donor system prior toallocating those resources. In other embodiments, the resource allocatorcan automatically assume full control of any resources donated by adonor system to the grid.

The grid resources may include part or all of the resources available totheir respective physical systems. Thus, for example, a logicalpartition may request grid resources from a grid, which in turn arephysically supplied to the grid by another logical partition on the samephysical system. Further, one or more of the systems associated with thegrid may have on-demand resources available to supplement the gridresources based upon the demands of the client. These on-demandresources generally refer to resources supplied with a system but thathave not been enabled by the manufacturer of that system. Themanufacturer can then charge the owner of the system, such as a hostservice provider, a separate fee to enable the on-demand resourceseither temporarily or permanently at some point after the system ispurchased. Thus, for example, a system may include on-demand processorsthat can be enabled whenever the purchaser desires additional processingcapacity by simply purchasing and entering an enablement code designedto enable the on-demand processors.

Because on-demand resources can be quickly and easily enabled at a latertime, the purchaser of a computer system can advantageously purchaseonly those resources necessary to satisfy their immediate requirements,as opposed to having to purchase extra capacity to allow for demandfluctuations and growth. On-demand resources are also desirable for themanufacturer of the computer system because it will be in a strongposition to sell that additional capacity when the purchaser needs toexpand.

The combination of the grid resources and the on-demand resources usedby some embodiments of the present invention is particularly desirablebecause it offers the host service provider with a highly flexibleresource capacity, and the clients with the opportunity to contract forthe resources to handle peak seasonal needs while contractingunderutilized resources back to the host service provider during theoff-season.

Embodiments of the present invention may monitor resource usage andmeter billable usage of the grid resources and/or on-demand resources bythe client. These embodiments frequently involve contractual agreementsbetween service providers and clients regarding when grid and/oron-demand resources will be made available to the client, as well as therates charged for each type of supplemental resource. These embodimentsalso frequently involve agreements between the host service provider anda manufacturer that sells computer systems with on-demand resourcesregarding the costs associated with enabling the on-demand resources.

One embodiment of the invention is implemented as a program product foruse with a computer system such as, for example, the system 100 shown inFIG. 1 and described below. The program(s) of the program productdefines functions of the embodiments (including the methods describedherein) and can be contained on a variety of signal-bearing media.Illustrative signal-bearing media include, but are not limited to: (i)information permanently stored on non-writable storage media (e.g.,read-only memory devices within a computer such as CD-ROM disks readableby a CD-ROM drive); (ii) alterable information stored on writablestorage media (e.g., floppy disks within a diskette drive or hard-diskdrive); and (iii) information conveyed to a computer by a communicationsmedium, such as through a computer or telephone network, includingwireless communications. The latter embodiment specifically includesinformation downloaded from the Internet and other networks. Suchsignal-bearing media, when carrying computer-readable instructions thatdirect the functions of the present invention, represent embodiments ofthe present invention.

In general, the routines executed to implement the embodiments of theinvention, may be part of an operating system or a specific application,component, program, module, object, or sequence of instructions. Thecomputer program of the present invention typically is comprised of amultitude of instructions that will be translated by the native computerinto a machine-readable format and hence executable instructions. Also,programs are comprised of variables and data structures that eitherreside locally to the program or are found in memory or on storagedevices. In addition, various programs described hereinafter may beidentified based upon the application for which they are implemented ina specific embodiment of the invention. However, it should beappreciated that any particular program nomenclature that follows isused merely for convenience, and thus the invention should not belimited to use solely in any specific application identified and/orimplied by such nomenclature.

Turning now to the drawings, FIG. 1 depicts an embodiment of a system100 for expanding resources available to a logical partition likelogical partitions 135 and 140. System 100 comprises a logicallypartitioned system 110, other system(s) 150, a LAN/WAN 160, clients 165and 170, and a system manufacturer 175. The logically partitioned system110 in this embodiment is configured such that the available systemresources, such as the processor(s) 115, a memory 120, and otherresources 125, can be allocated among multiple, logical partitions, suchas logical partitions 135 and 140. Each logical partition 135, 140 inthis embodiment is designed and configured to appear to operateindependently of the other. Thus, for example, one instance of theAdvanced Interactive Executive (AIX) operating system may be executingwithin logical partition 135, and one instance of the OS/400 operatingsystem may be operating within logical partition 140. The logicallypartitioned system 110 also includes on-demand resources 130, a capacitymanager 132, grid resources and/or access to grid resources 145, and aresource monitor/meter 147 to manage common pools of resources availableto supplement the resources of the logical partitions 135 and 140.

The processor(s) 115 in this embodiment include one or more system orhost processors that provide the processing capacity for logicallypartitioned system 110. A system operator can divide the processors 115into physical groups (e.g., processors 1-3 and 4-8) and assign them tothe logical partitions 135, 140. A system operator can also divide theprocessor(s) 115 into logical processor units and then assign thefractions of each processor 115 to the logical partitions 135, 140 inany ratio. For example, the system operator may provide 25% of oneprocessor to a logical partition 135 and 75% of the processor to logicalpartition 140. The system operator can also reserve processors and/orprocessor units for assignment to the logical partitions on demand.

The memory 120 may include one or more memory devices having blocks ofmemory associated with physical addresses, such as random access memory(RAM), read only memory (ROM), flash memory or other types of volatileand/or non-volatile memory. As with the processor(s) 115, the memory 120can be divided into physical blocks and associated with the logicalpartitions 135, 140, and/or can be divided into logical partitions vialogical blocks of addresses. The logical addresses can then be assignedto physical addresses as data is stored at the logical addresses.

The other resources 125 may include I/O controllers; I/O busses and I/Oadapters, such as peripheral component interconnect (PCI) cards couplinglogically partitioned system 110 with I/O equipment like tape drives;disk drives; hard drives; optical drives; network adapters; printers;scanners; etc. These other resources 125 may also be physically and/orlogically associated with the logical partitions 135, 140, either on anexclusive or shared basis.

The on-demand resources 130 may include resources that can be enabledlocally or remotely by the manufacturer 175, or by host service providerupon communication with the manufacturer 175, via the capacity manager132. The enablement of these resources 130 is typically based upon anagreement between the manufacturer 175 and the host service providerthat purchased or leased the logically partitioned system 110 from themanufacturer 175. These on-demand resources 130 may include additionalprocessors, memory, hard drives, compact disk drives, tape drives,optical drives, and the like, that are present, but disabled, in thelogically partitioned system 110 when purchased and that can be enabledupon payment of a predetermined fee.

The capacity manager 132 may provide metered capacity on demand tologically partitioned system 110 by enabling on-demand resources 130with an enablement code and metering usage of on-demand resources 130for the manufacturer 175. The resource monitor/meter 147 can thenallocate and meter portions of on-demand resources 130 for logicalpartitions. In particular, capacity manager 132 in this embodimentincludes an enablement code authenticator to verify that an enablementcode is valid.

In some embodiments, the host service provider may contract fortemporary availability of the on-demand resources 130 by requesting atemporary enablement code designed to expire in a number of, e.g.,resource-hours. This on-demand resource may be assigned and used in avariety of ways. For example, one 24 processor-hour enablement code maybe used to enable a single on-demand processor resource 130 for a 24hour period, or may be used to enable six processors for four hourseach. In several embodiments, the number or quantity of a resource canbe fractional, such as using 50% of processing capacity of a singleprocessor for 48 hours. In other embodiments, the agreement between theservice provider and the manufacturer may provide for unlimited usage ofall resources for a number of days at a single rate per day. Thecapacity manager 132 in these embodiments will recognize that thetemporary enablement code is invalid after its first use.

In still other embodiments, the host service provider may agree to payonly for actual usage of the enabled resources, and the capacity manager132 may monitor its actual usage. In these embodiments, the capacitymanager 132 may facilitate billing the service provider per minute orper hour of actual usage in terms of resource quantity and time ofon-demand resources 130. Periodically, or after the expiration of a timeperiod/resource quantity associated with a temporary enablement code,the actual usage may be communicated to the manufacturer 175 to generatea bill for the host service provider. The service provider, in turn,will use this information to generate a bill for the client associatedwith the logical partition that used the resource.

In several embodiments, the manufacturer 175 may charge the serviceprovider a single fee for an enablement code to permanently enable theon-demand resources 130, or a portion thereof, and the capacity manager132 may verify the permanent enablement code and permanently enablecorresponding on-demand resources 130. For example, a host serviceprovider may purchase a computer with four enabled processors and fouron-demand processors. The purchase agreement may provide the serviceprovider with the option to purchase additional processors at a rate perphysical processor or fractions of processing capacity. When thebusiness of the service provider expands, the host service provider maypurchase additional processing capacity available in on-demand resources130 by contacting the manufacturer 175 via LAN/WAN 170 and requesting anenablement code to permanently enable a certain fraction of processingcapacity. The manufacturer 175 in this example may then look up a codein the code 180 for host service provider's logical partitioned systembased upon, for instance, the model number and serial number oflogically partitioned system, or generate an enablement code based uponthe model number, serial number, the date of the request and thequantity-time value of processing capacity requested, and transmit theenablement code to logically partitioned system 110. The capacitymanager 132 in these embodiments will then interpret and authenticatethe enablement code received from the manufacturer 175 and enableon-demand resources 130 to provide the quantity-time value of processingcapacity purchased, an indication that the processing capacity is to bepermanently enabled in this case, for use by logically partitionedsystem 110.

One suitable method for providing access to on demand resources isdescribed in U.S. patent application Ser. No. (Atty Dkt. No.ROC9-2003-0071), entitled “Method to Provide On-Demand Resource Access,”which is herein incorporated by reference in its entirety. One suitablecapacity manager 132 for providing metered capacity on demand isdescribed in U.S. patent application (Atty Dkt. No. ROC9-2003-0147),entitled “Apparatus and Method for Providing Metered Capacity ofComputer Resources,” which is also herein incorporated by reference inits entirety.

The logical partitions 135 and 140 in this embodiment represent physicaland/or logical divisions of resources available from server 110 forclients 165 and 170. The division allows the logical partitions tooperate as independent logical systems, each having processing capacity,memory, storage capacity, and I/O devices. For example, logicalpartitions 135 and 140 may each have access to, e.g., 50% of theprocessing capacity of processor(s) 115, the memory 120, and the datastorage capacity of other resources 125. In this example, each logicalpartition 135, 140 is limited to using one half of the processingcapacity of one or more of the physical processors; a range of logicalmemory addresses, dynamically assigned to physical memory address via alook-up table; and one half of the data storage capacity by physicallydividing address ranges or providing a range of logical addresses. Someembodiments are capable of supporting 254 or more logical partitions.

Based upon agreements between the service provider associated withlogically partitioned system 110 and its customers, the logicalpartitions 135 and 140 may be associated with the grid resources 145,the on-demand resources 130, the capacity manager 132, and the resourcemonitor/meter 147. More specifically, the agreements between the serviceprovider and its customers may outline when and for what rate (or rates)the grid resources 145 and the on-demand resources 130 can be allocatedto logical partitions 135 and 140. The resource monitor/meter 147 willthen couple with the grid resources 145, the on-demand resources 130,and the capacity manager 132 to implement the agreement(s). For example,an agreement between the service provider and a customer associated withclient 165 may provide for grid resources to be made available, to anextent that they are not fully utilized or are underutilized, to logicalpartition 135 when usage of the resources provided to logical partition135 (referred to as partition resources) reaches or exceeds a partitionutilization threshold. An illustrative partition threshold may be 80% oftotal resource capacity of the partition resources. Thus, the hostservice provider may configure the resource monitor/meter 147 to monitorthe usage of partition resources by the logical partition 135 todetermine when usage reaches 80% of the total resource capacity of thepartition resources and, once the partition threshold is reached, todetermine what grid resources 145 can be allocated to logical partition135, if any, and then allocate those resources to the logical partition135.

The host service provider may configure the resource monitor/meter 147to retain a list of grid resources 145 from participating systems orpartitions that are registered as grid resources. The grid resources 145may couple with resource monitor/meter 147 to allocate and de-allocategrid resources 145 to and from logical partitions based upon usage ofresources by the logical partitions and partition thresholds. The listof grid resources 145 may include, e.g., physical and/or logicaldescriptions of processor resources, memory resources, and otherresources available for allocation as grid resources as well aspriorities and utilization threshold(s) for grid resources associatedwith the participating logical partitions. In other embodiments, gridresources may be available to systems and/or partition whether or notthey have registered resources with grid resources 145 for allocation asgrid resources.

The host service provider may configure the resource monitor/meter 147to monitor usage of partition resources, grid resources 145, andon-demand resources 130; to meter usages of resources having anassociated usage fee; and to maintain a log of usages on acustomer-by-customer basis for billing the corresponding customers. Insome embodiments, the resource monitor/meter 147 periodically generatesa bill for each client based upon the log and, in several of theseembodiments, automatically transmits the bill to the correspondingcustomers.

The host service provider may configure the resource monitor/meter 147to communicate with the logical partitions 135, 140 in order to monitorusage of partition resources and to allocate grid resources to a logicalpartition when the logical partition reaches or surpasses a thresholdutilization of partition resources. To an extent that grid resources areinsufficient to supplement resources available to a logical partition,the host service provider may configure the resource monitor/meter 147to, when necessary, allocate on-demand resources 130 to the logicalpartition. For example, when the logical partition 135 reaches apartition threshold (e.g. logical partition uses 20% out of the 21% ofprocessor clock cycles allocated to logical partition 135 fromprocessor(s) 115), the resource monitor/meter 147 may check for andallocate available grid resources 145. Later, when the resourcemonitor/meter 147 determines that grid resources 145 have reached autilization threshold for grid resources (e.g., 9% out of the 10% ofprocessor cycles registered by logical partitions 135 and 140 and pooledvia grid resources 145), the host service provider may configure theresource monitor/meter 147 to request that the capacity manager 132enable some on-demand resources 130. In response, the capacity manager132 requests and verifies an enablement code from the manufacturer 175,and then enables on-demand resources 130 to logically partitioned system110. The resource monitor/meter 147 can then allocate the on-demandresources 130 to logical partition 135, supplementing an allocation ofgrid resources based upon usage of resources by logical partition 135.

When allocating resources from on-demand resources 130 to logicalpartition 135, the customer associated with logical partition 135 may becharged a rate for usage based upon the agreement between the serviceprovider and the customer. For instance, the customer may be charged forone day of usage of on-demand resources for each day within whichlogical partition is allocated on-demand resources 130. In particular,logical partition 135 may be allocated on-demand resources for one hourof a first day; however, resource monitor/meter 147 may log a charge ofone day of usage to at least cover the costs of enabling on-demandresources for the customer. In some embodiments, the rate charged to thecustomer may depend upon the capacity of on-demand resources 130actually used by logical partition 135.

In further embodiments, the host service provider may configure theresource monitor/meter 147 to determine the rate based upon the portionof on-demand resources 130 enabled to accommodate an allocation ofon-demand resources 130 to logical partition 135. For example, anagreement between the service provider and the manufacturer 175 maystipulate units of on-demand resources 130 that must be enabled as awhole, such as one processor unit per hour. Thus, even though logicalpartition 135 may be allocated a half of a processor unit for an hour,resource monitor/meter 147 may meter the allocation to logical partition135 as one processor unit for an hour, or in some cases, for a day.

In still other embodiments, the host service provider may configure theresource monitor/meter 147 to determine a rate charged to the customerassociated with logical partition 135 for allocation of on-demandresources 130 based upon the number and/or capacities of allocations toother logical partitions or other systems 150. For example, when bothlogical partition 135 and 140 are allocated on-demand resources 130during the same day, resource monitor/meter 147 may charge logicalpartitions 135 and 140 reduced rates. The actual rates charged to thecustomers of logical partition 135 and 140, respectively, however, maydepend upon the agreements between the respective customers and theservice provider by, for instance, maintaining a representation of therates in memory or other data storage that is accessible by resourcemonitor/meter 147. In one embodiment, resource monitor/meter 147 maydetermine the rates charged to logical partitions 135 and 140 when theyshare the same portion of on-demand resources 130 at different timesduring the same day, divide the rates for the on-demand resources 130during that day, in half.

The host service provider may also configure the resource monitor/meter147 to log the allocations and/or usages of on-demand resources 130 andthe rates charged to customers for those allocations and/or usages. Insome embodiments, resource monitor/meter 147 may determine and log therates at the end of the day, periodically, or in response to a billingrequest by a client or the service provider, particularly when ratesdepend upon the number and capacities of allocations of on-demandresources 130.

In further embodiments, the host service provider may configure theresource monitor/meter 147 to allocate and de-allocate grid resources145 and/or on-demand resources 130 based upon requests from logicalpartitions like logical partitions 135 and 140. For example, whenlogical partition 135 reaches a utilization threshold for, e.g.,processing capacity, logical partition 135 may request that additionalprocessing capacity be allocated to logical partition 135 and, dependingupon the availability of grid resources, grid resources and/or on-demandresources 130 may be allocated in response to the request. In some ofthese embodiments, a higher utilization threshold may be set forrequesting on-demand resources 130 than grid resources 145. For example,logical partition 135 may request an allocation of grid resources whenthe utilization threshold of partition resources for logical partition135 has reached or exceeded 80% of partition resources. On the otherhand, the logical partition 135 may not request allocations of on-demandresources 130 until the utilization threshold of partition resources hasreached 100% and grid resources are unavailable.

In many embodiments, allocations of grid resources 145 may also beassociated with a rate. In such embodiments, the host service providermay configure the resource monitor/meter 147 to meter and log usageand/or allocations of grid resources 145 to a logical partition. Forexample, one processor unit of processing capacity from logicalpartition 135 may be registered with grid resources 145. Based upon anagreement between the customer associated with logical partition 135 andthe service provider, the logical partition 135 may be eligible toreceive allocations of up to 200% of registered resources, or twoprocessor units of processing capacity, from grid resources, ifavailable, at no additional cost. Thus, the resource monitor/meter 147may meter allocations or actual usage of grid resources by logicalpartition 135 to the extent that the allocations or actual usage exceedtwo processor units of processing capacity.

In some embodiments, agreements with customers may stipulate that therate charged for resources will vary depending on factors such as timeof day, time of year, and the like. For example, some host serviceproviders may configure the resource monitor/meter 147 to charge theclients more for capacity between 8:00 am and 6:00 pm, than between11:00 pm and 6:00 am, to reflect the higher demand for resources duringthe work day. Similarly, extra capacity during traditionally busyperiods, like December, may cost more than capacity in traditionallyless busy periods, like June and July. In several embodiments, theresource monitor/meter 147 may monitor, meter, and log usages ofindividual resources, such as processing capacity, memory capacity, harddrive capacity, and/or other capacities separately, and calculate feesdepending on the relative cost of each type of resource.

In another embodiment, agreements with customers may stipulate, andaccordingly, the host service provider may configure the resourcemonitor/meter 147 to allocate resources registered with grid resources145 on a first come, first serve basis. More specifically, when logicalpartition 135 registers a processor unit of processing capacity withgrid resources 145, that processing capacity may be allocated to logicalpartition 140 and remain unavailable to logical partition 135 until theprocessing capacity or a portion thereof is de-allocated from logicalpartition 140. In other embodiments, logical partitions may be assigneda priority for receiving grid resources (or resources at grid resourcerates) based upon, e.g., the quantity and time of partitions resourcesregistered with grid resources 145 or the amount charged for the use ofthe grid resources.

Agreements between the service provider and customers may also providefor allocation of on-demand resources 130. In these embodiments, thehost service provider may configure the resource monitor/meter 147 toautomatically enable and allocate on-demand 130 resources once autilization of grid resources reaches a grid utilization threshold. Thegrid utilization threshold, or grid threshold, may represent theutilization level associated with grid resources as a whole, i.e., allresources registered with grid resources 145. For example, gridresources may include two processing units of processing capacity. When100% of the grid resources have been allocated, resource monitor/meter147 may request that on-demand resources 130 are enabled via capacitymanager 132 so that subsequent allocations of processing capacity aremade from on-demand resources 130. The manufacturer 175 receives therequest and, if the request is authenticated, generates an enablementcode and returns the code to logically partitioned system 110. Thecapacity manger 132 receives the enablement code and verifies that thecode is valid. If the enablement code is valid, the capacity manager 132enables and meters on-demand resources 130 for the logically partitionedsystem 110. Then, the resource monitor/meter 147 may allocate and meterthe newly enabled on-demand resources to logical partitions 135 and 140.

In another embodiment, based upon an agreement between the serviceprovider and the customer associated with logical partition 135, thehost service provider may configure the resource monitor/meter 147 todetermine that the grid utilization threshold for logical partition 135has been reached when, for example, 80% of the total grid resources arebeing utilized by logical partition 135. Thus, when 80% of the totalgrid resources are being utilized by logical partition 135, the resourcemonitor/meter 147 may enable the on-demand resources 130 and allocateon-demand resources after grid resources are 100% allocated.

In still other embodiments, the host service provider may configure theresource monitor/meter 147 to enable on-demand resources based on anamount of usage of the grid resources over time. That is, if aparticular logical partition frequently requires grid resources 145, thehost service provider may configure the resource monitor/meter 147 toautomatically enable additional on-demand resources 130 for that client.These embodiments may be particularly desirable for use in environmentswhere the grid resources 145 are comparatively more expensive, buteasier to allocate for short periods, than the on-demand resources 130.In addition, the host service provider may configure some resourcemonitor/meter 147 embodiments to selectively enable on-demand resources130 or grid resources 145 based on which is better suited for aparticular system load. Thus, for example, if the resource monitor/meter147 in these embodiments determines that a particular job consists of alarge number of interdependent calculations, it will enable andselectively route the job to the on demand resources 130.

The other system(s) 150 may communicate and couple with the logicallypartitioned system 110. The other system(s) 150 may include systems likecomputers or logically partitioned systems that may participate orregister resources with grid resources 145. One or more of the othersystem(s) 150 may also include additional on-demand resources 155 thatcan be allocated to logical partitions 135 and 140. In some embodiments,for instance, the other system(s) 150 may include other computers orservers in the same cluster as logically partitioned system 110 suchthat resources of the other system(s) 150 can be shared via high speedloops (HSLs) like Opticonnect, LAN, and asynchronous transfer mode(ATM). Usage and/or allocations of on-demand resources 155 by logicalpartitions 135 and 140 may be metered and logged by resourcemonitor/meter 147.

The WAN/LAN 160 is a network connection to communicatively couple thelogically partitioned system 110 with client computers, such as clients165 and 170. In some embodiments, the WAN/LAN 160 may include a networkin an office coupled via Ethernet, ATM, OptiConnect, and the like. Insome embodiments, the WAN/LAN 160 also couples with the Internet via acable modem, a direct subscriber line (DSL), a T1 line, a T3 line, fiberoptic line, or the like. In further embodiments, the WAN/LAN 160 mayinclude a network of temporary connections such as connections via atelephone system. For example, logical partition 135 operates as a webserver allowing multiple customers to connect to a web siteindependently for facilitating business-to-customer (B2C) transactions.When a client business, like client 165 experiences a large number oftransactions concentrated in a short period of time, such as increasedseasonal sales during popular holidays, the processing requirements forprocessing business transactions with customers simultaneously orsubstantially simultaneously may be greater than the processing capacityavailable to logical partition 135. Thus, processing capacity availablevia grid resources 145 and/or on-demand resources 130 may be allocatedto logical partition 135 to handle the high seasonal processing demandsof logical partition 135.

Clients 165 and 170 may include one or more computer systems likenotebooks or desktop computers. Clients 165 and 170 may couple withlogically partitioned system 110 via a LAN or WAN like LAN/WAN 160. Insome embodiments, clients 165 and 170 couple with a relay device such asa hub or switch that connects to logical partitions 135 and 140 oflogically partitioned system 110.

The manufacturer 175 may be the manufacturer of logically partitionedsystem 110, or a representative thereof, that is accessible via theLAN/WAN 160 to obtain one or more temporary or permanent enablementcodes for on-demand resources 130. When the manufacturers are the same,the manufacturer 175 may also provide one or more temporary or permanentenablement codes for on-demand resources 155. In other embodiments, themanufacturer 175 is accessible by other means such as paper mail,courier, telephone, or facsimile.

In one embodiment, the manufacturer 175 is configured with an enablementcode generator, referred to herein as code 180. The code 180 in thisembodiment is an algorithm capable of generating an enablement code. Thecode 180 may be invoked by a request received from logically partitionedsystem 110 via LAN/WAN 160. In response to a request, the code 180generates the enablement code, which may be returned to the logicallypartitioned system 110 via the same network connection. Alternatively,the enablement code may be returned via a different network connection,e.g., a subsequent network connection or an altogether differentnetwork. In a particular embodiment, the enablement code is transmittedelectronically to an electronic mail application (e.g., Lotus Notes® orMicrosoft Outlook®; not shown) residing on the logically partitionedsystem 110. Lotus Notes is a registered trademark of InternationalBusiness Machines, Inc., and Microsoft Outlook is a registered trademarkof Microsoft, Inc. In yet another alternative, the enablement code isprovided to a representative of the host service provider (e.g., anadministrator) of logically partitioned system 110 via paper mail (i.e.,the postal service) or facsimile, for example.

Referring now to FIG. 2, there is shown an embodiment of an apparatus200 to expand resources for a logical partition. Apparatus 200 may bepart of or separate from but coupled with a logically partitioned systemand may include a specific purpose system like a state machine orspecific purpose processors, a general purpose machine configured bysoftware to execute aspects of the invention, combinations of the two,or the like. In particular, apparatus 200 may track usage of partitionresources by logical partitions, allocate grid resources and on-demandresources to the logical partitions in response to usage and meter usageof grid and/or on-demand resources that are associated with a rate basedupon agreements between the service provider associated with thelogically partitioned system and the clients. More specifically,apparatus 200 includes a grid associator 210, a resource monitor 220,on-demand resources 240, a resource meter 250, a capacity manager 230,and a billing generator 270.

Grid associator 210 may associate one or more logical partitions with agrid. The grid represent a list of resources pooled as grid resourcesfor allocation to logical partitions when the logical partitions reachutilization thresholds of their respective partition resources. Forexample, a logical partition of a first client may allocate partitionresources to the grid to negotiate a reduced rate for the partitionresources. In some embodiments, the client's use of partition resourcesmay increase during spring and summer so the client may negotiate forpartition resources sufficient or substantially sufficient for expecteddemands during the spring and summer and negotiate a reduced overallcost with the service provider by offering to register an anticipatedcapacity of underutilized partition resources to the grid during thefall and winter. At the same time, the service provider can encouragethe client to register the partition resources to the grid, since theclient can obtain allocations of grid resources and/or on-demandresources, if necessary, to supplement partition resources forunanticipated business during the off-season.

Resource monitor 220 monitors contemporaneous usage of partitionresources and grid resources to determine when to allocate andde-allocate grid and on-demand resources for a logical partition. Inother words, resource monitor 220 references with grid associator 210 tomonitor usage of partition resources associated with the logicalpartition and overall usage of grid resources, to allocate the gridresources and on-demand resources to the logical partition based uponutilization thresholds associated with the partition resources and thegrid resources. For example, the logical partition may reach autilization threshold, agreed upon by the service provider and theclient, which enables an allocation of additional resources such as gridresources or on-demand resources. Resource monitor 220 recognizes thatthe utilization threshold of partition resources has been reached orsurpassed and determines whether sufficient resources are available fromgrid resources to allocate resources to the logical partition. When theunallocated grid resources are insufficient to handle an allocation or autilization threshold for grid resources is reached, on-demand resources240 are enabled.

Utilization thresholds 222 may maintain utilization thresholds for eachlogical partition and for the grid resources. For example, a utilizationthreshold may be set to 80% capacity of total grid resources. Whenallocations of resources reach 80% of the total grid resources, resourcemonitor 220 may communicate with capacity manager 230 to request anenablement code for on-demand resources 240 such as a permanent ortemporary enablement code.

Similarly, a utilization threshold may be set for all logical partitionsor registered logical partitions such as 90% of partition resources oreach client may set individual utilization thresholds for grid and/oron-demand resources. For example, a utilization threshold for partitionresources may be set as 90% for enabling grid resources and 98% forenabling on-demand resources 240. Utilization thresholds may also betime-dependent. Thus, to continue the previous example, a system mayalso enable on-demand resources if a logical partition required gridresources for more than 15 hours during the previous 5 days.

In some embodiments, utilization thresholds 222 may also maintaindifferent utilization thresholds for different types of resources. Forinstance, the utilization thresholds for a logical partition may includeone or more utilization thresholds for processor allocations, one ormore utilization thresholds for memory allocations, and one or moreutilization thresholds for other types of resources. Further, when localand remote on-demand resources are available, different utilizationthresholds may be associated with the local and remote on-demandresources.

Resource allocator 224 may reference utilization thresholds 222 toallocate an underutilized portion of grid resources to a logicalpartition when the logical partition utilizes at least a utilizationthreshold of the partition resources. Further, resource allocator 224may allocate a portion of the on-demand resources 240 when the logicalpartition utilizes at least a threshold utilization of the partitionresources (such as 95%) and the grid resources that are available areinsufficient to supplement the partition resources of the logicalpartition based upon resource usage by the logical partition. Inparticular, resource allocator 224 may request an enablement code foron-demand resources 240, capacity manager 230 may enable on-demandresources upon receipt and verification of the enablement code, andresource allocator 224 may allocate on-demand resources amongst logicalpartitions based upon usage and/or requests by the logical partitions.

Capacity manager 230 may enable the on-demand resources upon receipt ofa valid enablement code. The enablement code may be received from amanufacturer, or an agent thereof, of a logically partitioned systemand, in this embodiment, is unique and configured for use only on aparticular machine (e.g., the specific logically partitioned system forwhich the enablement code was requested).

Capacity manager 230 may include a manufacturer code authenticator 235.Manufacturer code authenticator 235 may be invoked to verify anenablement code. As noted above, the enablement code is preferablyspecific to a particular machine. Accordingly, manufacturer codeauthenticator 235 determines whether the enablement code is configuredfor the particular system. If the enablement code is verified, theselected, on-demand resources 240 are enabled, e.g., hardware selectedbased upon a resource-time value, wherein a value associated withcapacity utilized is multiplied by a value representing the amount oftime the capacity is utilized, to determine the life of the enablementcode.

In one embodiment, “enabling” or “unlocking” resources operates to placethe resources into service (i.e., to perform their designated functionssuch as processing or storing, depending upon the resource). Inparticular, these resources may be placed into service for a period oftime. In another embodiment, enabling the resources does not place theresources into service, but merely makes the resources available forresource allocator 224. That is, enabling the resources unlocks theresources so that resource allocator 224 can allocate units of theresources to a logical partition, for instance, but does notautomatically give control of the resources to the operating system(s)on the logically partitioned system. It should be clear that regardlessof the manner in which resources are placed into service, the durationfor which the resources are in use (or at least available to be used ifneeded during continued operation of the system) may be predefined. Oncethe specified time limit expires, the enabled resources are disabledfrom further use.

Similar to grid resources, on-demand resources 240 may be any variety ofresources in a computerized apparatus. For instance on-demand resources240 may include software applications, firmware applications, andvarious types of hardware. In one embodiment, grid resources pool anumber of connections allowed to connect with a logical partition andon-demand resources 240 includes additional allowances that can bepurchased on a quantity per time basis.

Resource meter 250 communicates with the resource monitor 220 to monitorand log usage by logical partitions over time and associates the usagewith rates for billing the corresponding clients. Resource meter 250 mayinclude a grid resource meter 252, an on-demand resource meter 254, arate determiner 256, a client rate database 258, and a client usage log260.

Grid resource meter 252 may track usage of grid resources to determine arate to charge corresponding clients for allocations of grid resourcesto logical partitions. Grid resource meter 252 may also couple with ratedeterminer 256 to associate a rate with the usage of grid resources. Forexample, grid resources may be associated with a rate for usage toadvantageously offset costs associated with allocations of on-demandresources 240. In particular, a client may agree with the serviceprovider to pay a rate for usage of grid resources to receive anagreement from the service provider to reduce rates billed to the clientfor allocations of on-demand resources 240.

On-demand resource meter 254 may track usage of on-demand resources 240to determine a rate to charge corresponding clients for allocations ofon-demand resources 240 to logical partitions. On-demand resource meter254 may also couple with rate determiner 256 to associate a rate withthe usage of on-demand resource meter 254. For example, the serviceprovider may purchase a temporary enablement code having a resource-timevalue. On-demand resource meter 254 tracks the actual usage of on-demandresources by the client(s) so the service provider can recoup the costsinvolved with purchasing the enablement code by charging a rate toclient(s) for actual usage, or allocations based upon actual usage, ofon-demand resources 240.

Rate determiner 256 may determine rates to charge clients for usage ofgrid resources and/or on-demand resources 240. More specifically, ratedeterminer 256 may determine a rate based upon usage of the gridresources by the client to offset costs associated with enablingon-demand resources 240, a rate based upon usage of on-demand resources240 by the client to at least recoup costs associated with enablingon-demand resources 240, and/or a rate to charge the client based uponan agreement for allocations of the grid resources and the on-demandresources 240 to the logical partition associated with the client. Forexample, an enablement code to enable on-demand resources 240 may beoffered at a lower rate when the enablement code is associated with atime limit within which the resources may be utilized. The serviceprovider may purchase the enablement code and rate determiner 256 maysplit the costs between one or more clients based upon their actualusage or allocations based upon their actual usage of on-demandresources 240.

As another example, the enablement code may enable on-demand resources240 for, e.g., two months like November and December for the holidays,and the cost of the enablement code may be based upon the actual usageof on-demand resources 240 during the two months. As a result, to recoupthe cost of the enablement code, rate determiner 256 may split costsbetween clients associated with logical partitions that receivedallocations from the on-demand resources 240 during those two months. Insuch embodiments, rate determiner 256 may determine rates periodicallyto facilitate billing clients, or at the end of the two month period.

Rate determiner 256 may couple with grid resource meter 252 andon-demand resource meter 254 to associate the rates with usages byclients or with clients and may store the rates in client usage log 260.For example, when different rates may apply to usage of on-demandresources 240 depending upon usage by other clients or the agreementbetween a client and the service provider, the rates determined by ratedeterminer 256 may be associated with specific usages of the gridresources and/or on-demand resources 240. On the other hand, when asingle rate is charged for usage of grid resources and/or on-demandresources 240, the rate(s) may be associated with the client in theclient usage log 260 rather than with specific entries of usages for thecorresponding clients.

Client rate database 258 may include rates or formulas to determinerates based upon agreements between the service provider and clients. Insome embodiments, client rate database 258 may include individual ratesfor each client, rates for groups of clients, and/or default ratesselected by the service provider. For example, a group of clients, e.g.,clients that executed a first standard contract with the serviceprovider, may be charged the same rate for usage of grid resourcesand/or on-demand resources 240. The group rates may be stored in clientusage log 260 and the clients in the group may be associated with thosegroup rates.

Client usage log 260 may track allocations of resources to the logicalpartition to supplement the partition resources and one or more ratesassociated with usages like actual usages or allocations based uponactual usages.

Billing generator 270 may be configured to generate billing informationfor clients including, e.g., usages of grid resources and on-demandresources 240, rates associated with the usages and totals due for theusages. In general, the billing information may be generatedperiodically according to a predefined schedule, or on demand. In anycase, generation of billing information may be facilitated by clientusage log 260. For example, the resource meter 250 may write informationinto client usage log 260 including which resources are enabled and thecorresponding time value for the enabled resources. In some embodiments,resource meter 250 may also record resource usage information such asrequested time expired for a resource, requested time remaining for aresource, total runtime hours for a each enabled resource, the identityof the process or administrator that requested the On/Off capacity, andvarious enabled resource-specific metrics such as CPU cycles used, bytesof memory used, event timestamps, etc.

Information contained in client usage log 260 is retrieved by a billinggenerator 270 to generate bills or invoices for clients and transmit thebills to the clients or present the bill on a display upon request by aclient. Billing generator 270 may also retrieve or receive informationfrom other sources. For example, the billing generator 270 may retrievea current timestamp and date stamp. In one embodiment, the billinggenerator 270 invokes an algorithm (embodied in hardware, software orcombination thereof capable of producing an encrypted signature.Particular examples of encryption technology that may be used includechecksums, Digital Signature Standard (Federal Information ProcessingStandard 186-2), Elliptic Curve Crypto systems (ECC) and Data EncryptionStandard-Method Authentication Code (DES-MAC) and any other technology,known or unknown. In a particular embodiment, the encrypted signatureuses as input a variety of billing information provided by the billinggenerator 270 such as the contents of the log 132, for example to verifythe authenticity of selected essential items of the billing information.One suitable method for authenticating billing information is describedin U.S. patent application Ser. No. ______ (Attorney Docket NumberROC920030110), which is herein incorporated by reference in itsentirety.

Generally, billing generator 270 may be accessed locally (e.g., by anadministrator representing the service provider) or remotely (e.g., by aclient) for requesting, viewing, or printing a bill or a detailed listof usages by one or more clients along with the corresponding rates.Remote access may be facilitated, for example, by a TCP/IP connection.

Referring now to FIG. 3, there is shown an example of a flow chart 300for a method for expanding the resources available to a logicalpartition. Flow chart 300 begins with receiving a request or executingan agreement with a client to supplement partition resources of theclient's logical partition with grid resources and on-demand resources(step 310). For example, the agreement may include provisions forturning on or making allocations from grid resources and on-demandresources when the client's use of partition resources of the logicalpartition reach utilization thresholds such as a partition utilizationthreshold and a grid utilization threshold. The agreement may alsooutline rates, or formulas therefore, associated with allocations fromgrid resources and on-demand resources or the provision of gridresources to the grid.

The client's logical partition is associated with the grid (step 315).Associating the client's logical partition with the grid (step 315) mayinvolve an agreement between the service provider and the client toregister the client's logical partition with the grid. For example, theclient, in return for the opportunity to receive resource allocationsfrom grid resources, may register a portion of partition resourcesassociated with the client's logical partition to be used by the gridresource allocator.

The utilization thresholds agreed upon by the service provider and theclient may then be stored in the logically partitioned system andassociated with client's logical partition via a resource allocator(step 320). In some embodiments, a request may be made by the client toenable allocations of grid and on-demand resources by setting anindication that instructs a resource allocator to use these utilizationthresholds (step 320).

After the utilization thresholds are enabled, usage of partitionresources by the client's logical partition may be monitored (step 325)to determine when to allocate additional or supplemental resources tothe logical partition. Usage of the partition resources may be checkedcontinuously or periodically (step 330) until the usage of the partitionresources reach or exceed the partition threshold.

Once the partition threshold has been reached or exceeded, gridresources are checked to determine whether they are underutilized, oravailable for allocation to the logical partition (step 335). Then, theextent of the client's current allocations from grid resources may bechecked to determine whether the grid resources are available to theclient (step 340). For instance, in some embodiments, the client'sagreement with the service provider may provide that the logicalpartition may receive up to a certain allocation of grid resources suchas an allocation proportional to the portion of the partition resourcesregistered with the grid, or a straight percentage of grid resources,the remainder of grid resources being reserved for another customer(s).Once the logical partition exceeds the allotted share of grid resources,the logical partition may still receive allocations of grid resources,but, when another customer is allocated resources, and that customer hasnot surpassed an allotted share of grid resources, the client may beginto be charged for usage of on-demand resources and the customer may becharged a rate for grid resources, to the extent that on-demandresources were necessary to satisfy the allocation to the customer.

When grid resources are available to allocate to the client's logicalpartition, an allocation of grid resources may be enabled for use by theclient's logical partition (step 370). In one embodiment, enabling gridresources for use by the client's logical partition may involvedetermining a rate associated with use of the grid resources. The ratemay be determined based upon the actual usage of the grid resources orthe allocation made to the logical partition. For example, a rate may becharged to the client once the utilization of grid resources reaches 80%of the total grid resources or for allocations greater than oneprocessor unit of processing capacity to the same logical partition.Such rates may advantageously offset costs involved with enablingon-demand resources, for instance.

After enabling an allocation of grid resources for use by the client'slogical partition, usage of the grid resources by the logical partitionmay be metered and logged (step 375). The usage may also be associatedwith the client of the logical partition. In alternative embodiments,when clients are not charged for allocations from grid resources, steps370 and 375 may not be implemented.

Allocations of grid resources may then be checked to determine whetherthe utilization threshold for the total resources associated with thegrid has been reached or exceeded (step 380). For example, when the gridresources have been, e.g., 100% utilized, the service provider may wantto enable on-demand resources to assure that resources are available tothe client or other customers for additional allocations.

When sufficient grid resources are determined to remain available, theclient's allocation of grid resources continues to be metered (step385), or just provided when allocated at no cost to the client. On theother hand, if the usage of resources by the client's logical partitionfall below the partition threshold (step 385), grid resources that wereallocated to the client are de-allocated (when available to de-allocate)so the resources are available for subsequent allocations to the clientor other customers (step 390). The client's usage of partition resourcesis then monitored to determine when to provide a subsequent allocationof resources. In further embodiments, a hysteresis is built into thepartition threshold to prevent a cycle of repeated allocations andde-allocations of resources to the client's logical partition. Forinstance, when the partition threshold is set to 80% of the partitionresources, de-allocation of grid resources may not occur until the usageof partition resources fall below 70%.

When grid resources are unavailable to the client (step 340) or usage ofgrid resources reaches a grid threshold (step 380), subsequentallocations may include on-demand resources. When on-demand resourceshave not been enabled (step 345), an enablement code is requested andthe on-demand resources are enabled (step 350). Further, a rate for theclient for the allocation of on-demand resources to the logicalpartition is determined so the rate can be associated with theallocation or actual usage of the on-demand resources (step 350).

After the on-demand resources are enabled, usage such as actual usageand/or allocations to the logical partition may be metered and logged(step 355). The rate entered in the log and associated with the usagemay be determined and entered when allocations are made for the usage,periodically during the usage, or after enablement code for theon-demand resources has expired.

The grid threshold may be checked periodically or monitored continuously(step 360) to determine when the allocations of grid resources may besubstituted for allocations of on-demand resources (via steps 340 and370), removing or reducing the rate associated with the resourceallocation in some cases. When the usage of grid resources falls belowthe grid threshold (step 360), the on-demand resources may be disabledand de-allocated (step 365). For example, when the enablement code isprovided with a resource-time value, which enables the on-demandresources and accommodates various quantity and time combinations forthe use of on-demand resources, disabling the on-demand resources mayinvolve migrating use of current allocations of on-demand resources togrid resources, de-allocating current allocations of on-demandresources, and preventing subsequent allocations of on-demand resourcesuntil usage of the grid resources reach or exceed the grid threshold.Thus, on-demand resources from the same enablement code may be conservedfor subsequent allocations.

FIG. 4 depicts an example of a flow chart 400 for a method for billing aclient based upon usage of additional resources available to a logicalpartition. Flow chart 400 begins with contracting with a client toprovide for usage of on-demand resources by the client's logicalpartition (step 410). Contracting with the client may involve receivinga request or preferences (step 410). For instance, the client may beable to access the logical partition and check off preferences such as“associate this logical partition with a grid”, “enable allocations ofwhen the partition reaches or exceeds a utilization threshold”, “enableon-demand resources to meet resource capacity demands”, and the like.

When the partition threshold is exceeded, resources to be allocated fromthe grid are enabled (step 420). In other words, once the usage ofpartition resources reaches a utilization threshold, a request by thelogical partition for a resource, such as processing capacity, will beallocated from grid resources rather than partition resources. If gridresources are not available or the insufficient grid resources areavailable, for instance, the grid threshold may be reached or surpassedand resources are enabled and allocated to the logical partition fromon-demand resources (step 430). On the other hand, when sufficient gridresources are available for the allocation, the entire allocation may bemade from grid resources and the grid threshold may or may not reach thegrid threshold of utilization.

When the grid threshold is reached or surpassed, on-demand resources maybe enabled (step 430). For example, the service provider may permanentlyenable on-demand resources and recoup the costs by charging a rate forusing on-demand resources. Thus, allocations of on-demand resources oractual usages of on-demand resources may be associated with one or morerates based upon resource quantity and/or time via metering (step 440).

The client can then be billed for metered usage such as meteredallocations or metered actual usage, based upon the rates and/or rateformulas agreed to by the client (step 450). The bill may be presentedto the client electronically via a web server, an email, a facsimile,United States Postal Service, or the like.

FIG. 5 depicts an example of a flow chart 500 for a method for paying aclient based upon usage of the client's resources, which are madeavailable to a logical partition. Flow chart 500 begins with contractingwith a client to obtain client resources for grid resources (step 510).For instance, the client may have resources such as processing powerthat is idle for extended periods (e.g. over night) and may want toeither reduce rates for other services, receive discounts, register withthe grid resources, or receive some other form of payment such as cash.The client contracts with the service provider to make the idleresources available at certain times, upon request when and/or to theextent that client resources are idle, when the client indicates theresources are available, or the like. Then, the client's resources areenabled in step 520 to make them available for allocation to a logicalpartition, e.g., a logical partition for another client in a differenttime zone that can make use of the idle resources during the night.

When the partition threshold is exceeded, resources to be allocated fromthe grid are enabled (step 530). Priorities may be associated with gridresources from different client's based upon the client's agreement withthe service provider. For example, when the cost of the client'sresources is higher than the cost for other grid resources, the client'sresources may be selected last. In other circumstances, when multipleclients provide grid resources, an arbitration like scheme may beimplemented to make substantially equivalent use of the resources fromeach client.

Allocations of client resources or actual usages of client resources maybe associated with one or more rates based upon resource quantity and/ortime via metering (step 540). Then, the client can be paid based uponmetered usage and based upon the rates and/or rate formulas via paymentmethods agreed to by the client (step 550). For instance, the client mayreceive a rate reduction for grid resources, on-demand resources, orother resources and/or may receive direct payments. In some embodiments,the client's invoice/payment may request funds or include a checkdepending upon usage of the client's resources.

While the foregoing is directed to embodiments of the present invention,other and further embodiments of the invention may be devised withoutdeparting from the basic scope thereof, and the scope thereof isdetermined by the claims that follow.

1. A method for expanding resources available to a logical partitionassociated with a client, the method comprising: associating partitionresources of the logical partition with a grid; providing grid resourcesfrom the grid to the logical partition based upon usage of the partitionresources, wherein the grid resources are available to the logicalpartition; and providing on-demand resources to the logical partitionbased upon the usage of the partition resources and a usage of the gridresources when the grid resources are available to the logicalpartition.
 2. The method of claim 1, further comprising metering a usageof the grid resources by the client to determine a cost to assess theclient.
 3. The method of claim 1, further comprising metering a usage ofthe on-demand resources by the client to determine a cost to assess theclient.
 4. The method of claim 1, wherein associating partitionresources comprises enabling allocations from the grid resources to thelogical partition.
 5. The method of claim 1, wherein associatingpartition resources comprises registering with the grid at least aportion of partition resources associated with the logical partition, toallow the portion to be allocated to other logical partitions associatedwith the grid.
 6. The method of claim 1, wherein providing gridresources comprises: determining an unallocated portion of the gridresources and allocating the unallocated portion of the grid resourcesto the logical partition.
 7. The method of claim 1, wherein providinggrid resources comprises: determining that use of partition resourceshas at least reached a partition utilization threshold and allocating anunallocated portion of the grid resources to the logical partition. 8.The method of claim 1, wherein providing on-demand resources comprises:determining that use of partition resources has at least reached apartition utilization threshold; determining that sufficient resourcesare unavailable from the grid resources; and allocating an unallocatedportion of the on-demand resources to the logical partition.
 9. Themethod of claim 8, wherein providing on-demand resources furthercomprises: determining that usage of the grid resources has at leastreached a grid utilization threshold; requesting an enablement code toenable the on-demand resources; and allocating an unallocated portion ofthe on-demand resources to the logical partition.
 10. A method forexpanding resources available to logical partitions associated with aclient, the method comprising: registering resources with a grid as gridresources; allocating grid resources to the logical partition afterutilization of partition resources by the logical partition reaches afirst utilization threshold; allocating on-demand resources to thelogical partition after the logical partition reaches a secondutilization threshold for the grid resources; and billing the client forusage of the on-demand resources.
 11. The method of claim 10, furthercomprising billing the client for usage of the grid resources to offseta cost associated with enabling the on-demand resources.
 12. The methodof claim 10, wherein billing the client for usage of the on-demandresources comprises billing the client for the on-demand resourcesallocated to the logical partition based upon actual usage of theon-demand resources.
 13. The method of claim 10, wherein billing theclient for usage of the on-demand resources comprises billing the clientfor the on-demand resources allocated to the logical partition basedupon a quantity of the on-demand resources allocated and the amount oftime for which the quantity of the on-demand resources are allocated.14. An apparatus for expanding resources available to a logicalpartition associated with a client of a system having on-demandresources, the apparatus comprising: a grid associator to associate thelogical partition with a grid; a resource monitor coupled with the gridassociator to monitor usage of partition resources associated with thelogical partition and usage of grid resources associated with the grid,and coupled with the on-demand resources to allocate the grid resourcesand the on-demand resources to the logical partition based uponutilization thresholds associated with the partition resources and thegrid resources; and a resource meter coupled with the resource monitorto determine a first rate associated with an allocation of the on-demandresources to the logical partition for billing the client.
 15. Theapparatus of claim 14, wherein the resource associator comprises a listof resources associated with the grid to identify the grid resources.16. The apparatus of claim 14, wherein the resource monitor comprises aresource allocator to allocate an unallocated portion of grid resourcesto the logical partition when the logical partition utilizes at least athreshold utilization of the partition resources.
 17. The apparatus ofclaim 14, wherein the resource monitor comprises a resource allocator torequest an enablement code for the on-demand resources and to allocate aportion of the on-demand resources to the logical partition when thelogical partition utilizes at least a threshold utilization of thepartition resources.
 18. The apparatus of claim 14, wherein the resourcemeter tracks usage of grid resources by the logical partition todetermine a second rate to charge the client for allocating the gridresources to the logical partition.
 19. The apparatus of claim 14,wherein the resource meter comprises a rate determiner to determine thefirst rate based upon usage of the grid resources by the client, tooffset costs associated with enabling the on-demand resources.
 20. Theapparatus of claim 14, wherein the resource meter comprises a ratedeterminer to determine the first rate based upon usage of the on-demandresources by the logical partition to at least recoup costs associatedwith enabling the on-demand resources.
 21. The apparatus of claim 14,wherein the resource meter comprises a rate determiner configured todetermine the first rate to charge the client based upon an agreementfor allocation of the grid resources and the on-demand resources to thelogical partition.
 22. The apparatus of claim 14, wherein the resourcemeter comprises a usage log to log allocations of resources to thelogical partition to supplement the partition resources for charging theclient based upon the allocations.
 23. A computer readable mediumcontaining a program which, when executed, performs an operation,comprising: associating partition resources of a logical partition witha grid; providing grid resources from the grid to the logical partitionbased upon usage of the partition resources, wherein the grid resourcesare available to the logical partition; and providing on-demandresources to the logical partition based upon the usage of the partitionresources and usage of the grid resources when the grid resources areavailable to the logical partition.
 24. The computer readable medium ofclaim 23, wherein the operation further comprises metering the usage ofthe grid resources utilized by the logical partition to determine a costto assess a client associated with the logical partition.
 25. Thecomputer readable medium of claim 23, wherein the operation furthercomprises metering the usage of the on-demand resources utilized by thelogical partition to determine a cost to assess a client associated withthe logical partition.
 26. The computer readable medium of claim 23,wherein associating partition resources comprises enabling allocation ofthe grid resources to the logical partition.
 27. The computer readablemedium of claim 23, wherein providing grid resources comprises:determining that use of partition resources has at least reached apartition utilization threshold and allocating an unallocated portion ofthe grid resources to the logical partition.
 28. The computer readablemedium of claim 23, wherein providing on-demand resources comprises:determining that use of partition resources has at least reached apartition utilization threshold; determining that sufficient resourcesare unavailable from the grid resources; and allocating an unallocatedportion of the on-demand resources to the logical partition.
 29. Thecomputer readable medium of claim 23, wherein providing on-demandresources further comprises determining that usage of the grid resourceshas at least reached a grid utilization threshold; requesting anenablement code to enable the on-demand resources; and allocating anunallocated portion of the on-demand resources to the logical partition.30. A method for managing and controlling allocation of resources of alogical partition, comprising: providing grid resources to the logicalpartition based upon usage of partition resources; and providingon-demand resources to the logical partition based upon the usage of thepartition resources and a usage of the grid resources.
 31. The method ofclaim 30, wherein providing grid resources to the logical partitioncomprises: determining that use of partition resources has at leastexceeded a partition utilization threshold; and in response to thedetermining, allocating the grid resources to the logical partition. 32.The method of claim 31, wherein providing the on demand resources to thelogical partition comprises: determining that use of grid resources hasat least exceeded a grid utilization threshold; and in response to thedetermining, allocating the on demand resources to the logicalpartition.
 33. The method of claim 32, wherein the grid utilizationthreshold comprises an amount of grid resources used during apredetermined amount of time.
 34. The method of claim 30, furthercomprising: applying a first fee for use of the grid resources; andapplying a second fee for use of the on-demand resources.
 35. The methodof claim 34, wherein at least one of the first fee and the second feevary based on a factor chosen from the group consisting of a time of dayand a time of year.
 36. A method for deploying a computer application ona host service provider system, comprising: installing a computerapplication on a logical partition of a computer system, the computersystem having on-demand resources associated therewith; associating thelogical partition with a grid, the grid having grid resources associatedtherewith; configuring the computer system to provide the grid resourcesto the logical partition based upon usage of the partition resources;and configuring the computer system to provide the on-demand resourcesto the logical partition based upon a usage of the grid resources. 37.The method of claim 36, further comprising: applying a first fee for useof the grid resources; and applying a second fee for use of theon-demand resources.